(103/185) 238 - EditorConfig: support for editing files over remote VFS

Perhaps "path regex" makes more sense than "server" since server only means something when you are using the FTP plugin.
A mapping of path regexes to encodings would be quite convenient.
Perhaps that should also include line separator character.

- **summary**: Default character encoding per server --> Default character encoding per path regex

ezust, you're right, particularly about line separator (I forgot about it).

From other hand, different charsets are rare when on the same machine. It is much more hot for remote servers, so I would put "path/server" in the topic.

- **summary**: Default character encoding per path regex --> Default character encoding per path/server regex

> From the file system browser, you can right click a folder and go to
encoding, and select the default encoding for opening files under that
location. How different is that from what you are asking?

Hmm.. Didn't know about this opportunity.
Though, encoding chosen for a particular folder resets every time default encoding is changed.
Encoding settings are not portable between installations as well.
Considering aforementioned, I think those settings should be saved somewhere explicitly.

I am not sure if this works on remote file systems, but the EditorConfig plugin allows you to specify an encoding of all files in a directory, via a .ini file

EditorConfig doesn't yet set encoding for jEdit. Opened an issue about it.
https://github.com/editorconfig/editorconfig/issues/95

Moving to Plugin Feature Requests.
This can be done in a plugin. EditorConfig handles 5 standard encodings while jEdit can handle many others.

- **summary**: Default character encoding per path/server regex --> EditorConfig: set character encoding per path/server regex

Git master of EditorConfig plugin now supports jedit_encoding which means half of this feature request is
satisfied by EditorConfig.
How to handle Remote VFS is a problem that is under discussion still. Currently, EditorConfig loads its .editorconfig files with java.io.file instead of the more generic VFS API.
If EditorConfig could load remote .editorconfig files like jEdit does, this would solve the problem.

- **assigned_to**: nobody --> xuhdev

Correct @ezust a detail:

jedit_charset not jedit_encoding

New ticket opened for handling remote VFS:
https://github.com/editorconfig/editorconfig/issues/101#issuecomment-17088076

- **summary**: EditorConfig: set character encoding per path/server regex --> EditorConfig: support for editing files over remote VFS